Updating tutorial with clarification for the naming conventions #16767
Conversation
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
1 similar comment
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. |
|
need to update my other PR, cancelling this |
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Documentation update
What is the current behavior? (You can also link to an open issue here)
When I was reading the tutorial a section of how controller naming was unclear to me.
What is the new behavior (if this is a feature change)?
Adds some clarification to the docs
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements
Other information:
Did an initial PR here. Not sure how to update that one, so I instead created a new one.
#16740 (comment)